Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference
471-tree-1
name
1662
tree-preservation-order

undefined

471-tpo-1
uprn
address-text
point
POINT (-1.023796 50.882668)
geometry
MULTIPOLYGON (((-1.023725 50.882661,-1.023729 50.882675,-1.023738 50.882687,-1.023754 50.882697,-1.023774 50.882704,-1.023796 50.882706,-1.023818 50.882704,-1.023838 50.882698,-1.023853 50.882688,-1.023864 50.882676,-1.023868 50.882662,-1.023864 50.882648,-1.023855 50.882635,-1.023839 50.882625,-1.023819 50.882619,-1.023797 50.882616,-1.023775 50.882618,-1.023756 50.882625,-1.023740 50.882634,-1.023729 50.882647,-1.023725 50.882661)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL